Can you make use build-time variables instead? That would allow for a more flexible to build the Docker Image. See #550 for some ideas I had in mind.

Do we need this flexibility? I'm asking because I prefer to add the minimal needed abstraction only. In addition, I suggest to distinguish between fixing and enhancing the image.

Other ideas for enhancements:

1. Do we need the debian-based builds? Afaik, docker is used only by the pre-commit hook, which in turn uses the alpine-based image only.
2. @Kampfkarren As the build pipeline shows, the built images are pushed to the Docker hub. But under which account? Shall we document the location of the builds?

Do we need this flexibility? I'm asking because I prefer to add the minimal needed abstraction only. In addition, I suggest to distinguish between fixing and enhancing the image.

Don't fix what's not broken is definitely the easier way around the issue with the Docker build issue right now tbh. The flexible enhancements I suggested on the other hand is to future-proof a potential scenario wherein someone had to test the build against a different Rust Docker Image for whatever reason.

For example, what if someone had to quickly check if a certain feature works on a particular Image or perhaps a specific version of Rust? Passing the build-time variables to docker would allow us to do that.

The other intention I had in mind was, since the current Dockerfile is worked on, why not do it the proper way right now instead of waiting for someone else to do it in the future? It'll allow Kamp to be relieved off of some maintenance burden as well.

@f1rstlady My assumption for the account is going to be boyned. This looks fine